more

HCL Notes/Domino 8.5 Forum (includes Notes Traveler)

Subject:

in random order!

- the old java editor had all the java source available in one window, and simply had to expand the section for the first one. We could look at opening the first Java file *in addition* to the project page - would that be helpful? One of our earliest designs *did* try expanding things in the navigator - but that encountered virtual file system difficulties. We can look at it again, as it was a design we liked, it just is not as easy or doable as it may appear - particularly since we would need to materialize a linked project just to expand that thing.

I spent some time this morning opening some java agents, and I'm not seeing 20 second delays. Now there could be differences in the agent and/or the hardware, but it seemed no worse than the old Java editor to me (which always took a hit for at least the first instance to do some jvm loading). Could you possibly send me a troublesome agent so we can do some testing/tuning on opening it?

It is a good idea to add Run agent to the navigator (I am also wanting the preview function there). We will look at adding that. I do know that several people have extended Designer using the extension API to add that! That's always a very good clue that that's a much needed core change.

that ini setting is exactly what I was thinking we'd turn into a preference, and if it isn't working, then we broke it and should fix it. Since it's an unsupported ini, it likely didn't get caught, but it was unintentionally broken, so we will intentionally fix it.

We'll also see how the property panel got too bouncy, what stepped on that code to make it do that.

Thanks for your help!

Feedback response number MLED7XANKJ created by ~Keiko Froponepulflar on 10/29/2009